You can use the same ReqI for multiple buttons (React Node InSim always uses 1 too), but each button must have a unique ClickID (0-239).

You can view the source code of the TextBox component: https://github.com/simbroadcasts/react-node-insim/blob/main/src/lib/components/ui/TextBox.tsx

I think the logic and button structure could be rewritten into C# - it's a bunch of InSim buttons carefully placed together with some logic handling the scroll position and text splitting into multiple lines, but the part about displaying and updating the buttons needs to be handled differently since C# doesn't have a renderer like I have in React Node InSim.

I'm sorry but why do people tend to switch to DM all the time after asking a question? The point of this being in a public forum is that anyone can contribute and help you out. You can just continue in this thread.

Or you could show a message when a race session starts in the middle of the screen maybe using /rcm message, InSim buttons or chat message.

He just explained why it wouldn't be a good idea to expose this information via InSim.

What is your handbrake assigned to? Is it an axis or a button?

There is no way to get the green light event through InSim because if it was possible people would use it to cheat and get a perfect start.

Quote from chucknorris :

None of that does really compensates a potential loss of the IP address.
As for TC, I can say that many of our security related functions rely on the IP address.

Such as:
- Detect ban evasions
- Detect stolen accounts
- Detect VPN/proxy usage
- Detect the user's country

I'm trying to understand how "allowing hosters to identify if someone uses multiple user names from one computer" and "allowing hosters to identify if the same user name is used from multiple computers" does not compensate for a loss of IP address. To my understanding, people evade bans by using multiple LFS accounts. Stolen accounts are the same user name joining from multiple computers. Scawen also mentioned sending the country code separately. What am I missing here?

But why is that? Is it a bug or a limitation of the layout system?

Several people have reported an issue during their LFS account creation - they never receive the confirmation e-mail after registration:

Quote from LowSpec Racing --HOW-- :

Classic 80's Hot Hatches like lookalikes of Ford XR3i, Vauxhall/Opel Astra GTE, Golf GTI, etc

Group B rally legends like Lancia Stratos, Audi Quattro, Metro 6R4, etc.

Group B:
Lancia Delta HF
Lancia Stratos
XF Turbo 5

Last edited by Flame CZE, Thu 24 Apr 2025, 08:16.

Model authorisation does not belong in a work in progress thread, it belongs to the "Private agreement" field in the mod submission form (which you have done already).

Quote from WildGamerz :

1 more thing if im connected to insim relay how can i create commands if Prefix field is ignored when Isrelayhost = true; in insimdotnet lib tho

Is there a reason you use InSim Relay to communicate with your server? If you want to create commands etc. you can just connect to your server directly via InSim

How do you test that it doesn't work? I see you're sending an IS_MTC packet which won't work via InSim Relay unless you connect to the host with the correct admin password using the IR_SEL packet.

Only a subset of InSim packets are allowed to be sent / received:

Quote :

Regular insim packets that a relay client can send to host :

For anyone
TINY_VER
TINY_PING
TINY_SCP
TINY_SST
TINY_GTH
TINY_ISM
TINY_NCN
TINY_NPL
TINY_RES
TINY_REO
TINY_RST
TINY_AXI

Admin only
TINY_VTC
ISP_MST
ISP_MSX
ISP_MSL
ISP_MTC
ISP_SCH
ISP_BFN
ISP_BTN

The relay will also accept, but not forward
TINY_NONE // for relay-connection maintenance

For the whole documentation, see the original InSim Relay thread by Victor:

https://www.lfs.net/forum/thread/30740

Some people use LFS Editor to create the entire 3D model, others use Blender to create the 3D model, then export it as an OBJ file, which can be then imported into LFS Editor.

LFS Editor manual
LFS Editor video tutorials

For which car?

I have USB sleep disabled and MOZA Pit House not running and yet it happened again during a race today

Last edited by Flame CZE, Wed 23 Apr 2025, 07:29.

Quote from Scawen :

So we are left with, what problems could arise? The only issue I see is that someone could load a mod in our editor and export the plain grey model, which might be a breach of someone's "no derivatives" license. The proposed export function just makes it easier to get a 3D model out from an LFS mod, to be used somewhere else. It doesn't really allow anything that wasn't possible anyway, just makes it easier.

This will also make it easier to get access to 3D models that were purchased from 3D asset websites like (Sketch)fab or CGTrader.

I have moved the off-topic mod usage discussion: https://www.lfs.net/forum/thread/111116

Motorcycle gearboxes are a bit different - you must shift down in order to get into 1st gear.

Once you get going, you will notice that at low speeds, you control the bikes handlebars directly, but once you get up to speed, you control the lean of the bike instead. This means you need to be more gentle with the steering and start steering a bit earlier than you'd expect.

Last edited by Flame CZE, Tue 15 Apr 2025, 05:40.

I'm afraid even that is not allowed:

Quote from Scawen :

[...]

What is not allowed

[...]

4) Any other use of models or images extracted from another game to help in building a mod. No part of your mod creation process can involve using another game's content in defiance of the license agreement for that game.

It depends on the mod, but usually the doors/hood/roof are bound to the extra light function, which can be toggled by the /light extra toggle command.

I had the same issue. The wheel kept disconnecting at random times during gameplay.

I fixed it by completely closing the Moza Pit House software before playing LFS. I only open it if I want to adjust some settings.

Some people also suggest disabling power saving for the USB device of the wheel.

Last edited by Flame CZE, Mon 14 Apr 2025, 07:12.

Actually communicating with InSim is the easier part You listen for specific packets coming from LFS telling you about the current state of the car (speed, acceleration, position etc.) and then send other packets telling the AI car what to do (turn the wheel, accelerate, brake etc.) in regular intervals like every 100 ms.

I've got a very early prototype where I tell an AI car to drive at a constant speed using a PID controller:



Source code here

The harder part is to make it so that it follows the given path, obeys traffic rules, avoids collisions etc.